Let's use

Someone has shared a public link to a calendar on $theme->getName()

Instead then. You don't need to do anything with the l10n files, it will be handled automatically.

@tcitworld

I'm not sure I understand — you're telling me that there is an automatic translation engine in place behind the $l->t(...) method that would allow me to simply update my PR as follows and have the string get translated automatically, even though Someone has shared a public link to a calendar on %s does not exist in any of the l10n files? If so, that's awesome. Otherwise, please explain further. Thanks for the help! 😃

diff --git a/templates/main.php b/templates/main.php
 
 /* OpenGraph */
 if($_['isPublic']) {
 	OCP\Util::addHeader('meta', ['property' => "og:title", 'content' => $theme->getName() . ' - ' . $theme->getSlogan()]);
-	OCP\Util::addHeader('meta', ['property' => "og:description", 'content' => $l->t('Public access')]);
+	OCP\Util::addHeader('meta', ['property' => "og:description", 'content' => $l->t('Someone has shared a public link to a calendar on %s', [$theme->getName()])]);
 	OCP\Util::addHeader('meta', ['property' => "og:site_name", 'content' => $theme->getName()]);
 	OCP\Util::addHeader('meta', ['property' => "og:url", 'content' => $_['shareURL']]);
 	OCP\Util::addHeader('meta', ['property' => "og:type", 'content' => "object"]);

I'm not sure I understand — you're telling me that there is an automatic translation engine in place behind the $l->t(...) method that would allow me to simply update my PR as follows and have the string get translated automatically, even though Someone has shared a public link to a calendar on %s does not exist in any of the l10n files? If so, that's awesome.

That is exactly what he meant ;) Nextcloud uses Transifex for handling translations, so strings to be translated are collected by transifex, translated there and pushed back to the repo. No need to translate anything here.

We can be more specific, no? Instead of the bland

Someone has shared a public link to a calendar on Nextcloud

let’s go with

Georg shared the calendar Release planning

The important things are the name of the sharer and the calendar name. :)

We can be more specific, no?

I’m afraid this is not that easy at the moment. We only get the sharer name and display name of the calendar after sending some CalDAV requests in JavaScript.
So we don’t know that value when rendering the template yet.

We will have to implement some API in the dav app for that

Then yeah, let's implement that to make it happen. ;) "Someone shared …" is really a bit strange.

Just a quick update: I didn't take the time to implement the above yet, but I just wanted to let you all know that I (partly) fixed the issue on the Synapse side of things (Riot.fm is powered by Synapse): matrix-org/synapse#2576.

@maximevaillancourt do you need any help with this? Feel free to ask. :)

Closing in favour of #609

See for updated information.